Shared System Options

Select "Yes" to allow the system to signal diversion requests to the network. If this feature is disabled (by selecting "No"), the system still responds to diversion requests (from QSIG or DPNSS), but does not signal them. It is strongly recommended to have this option enabled.

NOTE: This feature affects the operation of some Cancel Call Forward features (see Call Forward).

Yes

Indicates whether to enable authentication for Computer Telephony Integration (CTI) applications that interact with the MiVoice Business system. For example, MiTAI applications, such as NuPoint VM, MiCollab, MiVCR, and MiCC.

NOTES:

• Ensure that MiTAI applications support CTI application authentication. For more information, refer to the application's documentation.

• If enabled, the setting is applied to all the MiVoice Business systems in a cluster running the MiVoice Business Release 9.0 software.

• If enabled, ensure that you enter the Login Id and Password, and select the Application check box in the User Authorization Profiles form.

• If enabled, third party applications using SXOpenPBX API of SDK 6 or earlier will not be able to connect to the MiVoice Business system.

No

Select "Yes" to allow a PSAP emergency callback to be routed to an emergency caller's registration telephone DN or hot desk user DN (see Emergency DID Routing).

Indicates whether to enable or disable Mitel emergency traps.

NOTES:

• Ensure that SNMP service status is enabled and SNMPv2c community string for read-write access is configured in Server Manager for all MiVoice Business Release 9.0 network elements in the cluster.

For Container-based MiVoice Business (cMiVB), ensure that Status is Enabled and SNMPv2c community string for read-write access is configured in Solution Manager.

• The system supports ER traps only with ER Adviser, Mitel Performance Analytics (MPA),  Mitel Mass Notification (MMN), and Mitel Revolution. For more information on programming emergency services notification, see Emergency Services - ER Application Notification Programming.

• Any changes to this parameter may take up to 100 seconds for changes to take effect.

• If you enable this parameter, the Trap host or address for ER Notification and TRAP Community String fields are mandatory.

No

Enter the IP address or FQDN of the primary SNMP Manager (for example, Mitel Revolution) that will receive the ER trap notification.

NOTES:

• If you enable Enable ER TRAPS, then this field is mandatory.

• If the SNMP Manager is setup for resiliency, then you can specify the IP address or FQDN of the secondary SNMP Managers in the Trap IPAddress/FQDN for ER Notification Optional 1 and Trap IPAddress/FQDN for ER Notification Optional 2 fields. The system sends the ER trap notification to primary and secondary SNMP Managers. However, when one of the SNMP Managers (primary or secondary) acknowledges the trap notification, the system stops sending the ER trap notification.

Blank

Enter the IP address or FQDN of the secondary SNMP Manager that will receive the ER trap notification.

NOTE: The ER trap notification is sent to primary and secondary SNMP Managers. However, when one of the SNMP Managers (primary or secondary) acknowledges the trap notification, the system stops sending the ER trap notification.

Blank

If there are two secondary SNMP Managers, then enter the IP address or FQDN of the second secondary SNMP Manager that will receive the ER trap notification.

NOTE: The system sends the ER trap notification to primary and secondary SNMP Managers. However, when one of the SNMP Managers (primary or secondary) acknowledges the trap notification, the system stops sending the ER trap notification.

Blank

Enter the trap community name (up to 20 characters) of the corresponding SNMP Manager. This value must be the same as entered in the ER application, such as ER Advisor, Mitel Performance Analytics (MPA),  Mitel Mass Notification (MMN), and Mitel Revolution. Enter the same value in the SNMPv2c community string for read-write access field in the Server Manager or Solution Manager.

NOTE: If you enable Enable ER TRAPS, then this field is mandatory.

Blank

Indicates whether to enable access to the Server Manager application from the MiVoice Business tool selection page.

If you select Yes, then the Server Manager button is displayed in the MiVoice Business tool selection page when you log in to the MiVoice Business system next time.

NOTES:

• Not applicable to Container-based MiVoice Business (cMiVB).

• You must have an administrator access or must be defined in the Server Manager database as a user to open the Server Manager application directly from the MiVoice Business tool selection page. Otherwise, you will be directed to the Server Manager login page to enter your credentials to open the Server Manager application.

• Ensure that Access to Server Manager is enabled for the user in the User Authorization Profile form.

No

Select "Yes" to enable the system to maintain and display on the nominated party's telephone or console the original reason for forwarding or rerouting a call. Select "No" to disable this functionality.

NOTE: To enable this functionality in a network or cluster configuration, option DPNSS/QSIG Diversion Enabled must also be set to "Yes" on all MiVoice Business systems in a network or a cluster.

Yes

Select "Yes" to maintain the original DNIS information on subsequent presentations of a call—for example, on re-queue or on transfer. If set to "No" the original DNIS information may, under certain circumstances, be lost on calls between local and remote nodes in a network environment.

This option works for the following trunks which are capable of ANI/DNIS/ISDN number delivery to the Mitel private network:

• ISDN

• DASS 2

• Analog trunks with the ANI/DNIS/ISDN Number Delivery COS option enabled

• TI/D4 trunks with the ANI/DNIS/ISDN Number Delivery COS option enabled

• QSIG

• DPNSS

For QSIG trunks, the calls must originate in the public network. Original DNIS will not be extended over QSIG trunks within the Mitel private network.

For DPNSS trunks, the calling line category must be CLC-ISDN (CLC-DASS2).

The original DNIS digits presented will be either those received from the trunk or those after incoming digit modification is performed as controlled by the COS option, Display DNIS/Called Number Before Digit Modification.

No